|
|
|
|
|
BlueCielo Publisher 2012 Administrator's Guide | BlueCielo ECM Solutions |
A .NET Framework 2.0 managed assembly (such as is included in Publisher) that has an Authenticode signature takes longer to load than an assembly without a signature. The signature is always verified when the managed assembly is loaded. Additionally, the managed assembly may take longer than usual to load because of various other settings, for example, because of the network configuration.The common language runtime (CLR) tries to verify the Authenticode signature at load time to create publisher evidence for the assembly. However, by default, most applications do not need publisher evidence since a standard code access security (CAS) policy does not rely on the publisher evidence. You should avoid the unnecessary startup time associated with verifying the publisher signature unless your application executes on a computer with a custom CAS policy or you need to satisfy security requirements in a partial-trust environment. (Demands for identity permissions always succeed in a full-trust environment.)
We recommend that you disable the generatePublisherEvidence element in the .NET Framework 2.0 configuration files to improve startup performance. Because this involves both the client computers as well as servers, we recommend that this only be done on those computers that actually experience inadequate load times. To do this, add the following code:
<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>
To the following files on 32-bit computers:
To the following files on 64-bit computers:
When you disable signature verification, the .NET Framework 2.0 managed application starts faster. For more information, see the following Microsoft resources:
<generatePublisherEvidence> Element on MSDN
|
Copyright © 2000-2012 BlueCielo ECM Solutions |